FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource ValueSet/FHIR Server from package hl7.fhir.us.davinci-crd#current (47 ms)

Package hl7.fhir.us.davinci-crd
Type ValueSet
Id Id
FHIR Version R4
Source http://hl7.org/fhir/us/davinci-crd/https://build.fhir.org/ig/HL7/davinci-crd/ValueSet-AdditionalDocumentation.html
Url http://hl7.org/fhir/us/davinci-crd/ValueSet/AdditionalDocumentation
Version 2.1.0
Status active
Date 2024-12-11T01:38:49+00:00
Name CRDAdditionalDoc
Title CRD Coverage Information Additional Documentation Value Set
Experimental False
Realm us
Authority hl7
Description Codes defining whether additional documentation needs to be captured

Resources that use this resource

StructureDefinition
CRDMetricData CRD Metric Data
ext-coverage-information Coverage Information
http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/DTRMetricData DTR Metric Data

Resources that this resource uses

CodeSystem
temp CRD Temporary Codes


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ValueSet AdditionalDocumentation

  • Include these codes as defined in http://hl7.org/fhir/us/davinci-crd/CodeSystem/temp
    CodeDisplayDefinition
    clinicalClinical DocumentationDetails most likely to originate from a clinician are required to satisfy additional documentation requirements, determine coverage and/or prior auth applicability - e.g. via DTR by clinician. Indicates that the CRD client should expose the need to launch DTR to clinical users.
    adminAdministrative DocumentationAdministrative details not likely to require clinical expertise are needed to satisfy additional documentation requirements, determine coverage and/or prior auth applicability - e.g. via DTR by back-end staff. Indicates that while the CRD client might expose the ability to launch DTR as an option for clinical users, it should be clear that clinical input is not necessary and deferring the use of DTR to back-end staff is perfectly appropriate. Some CRD clients might be configured (based on provider preference) to not even show clinicians the option to launch.
    patientAdministrative & clinical docDetails most likely to originate from the patient or their personal representative (e.g. parent, spouse, etc.) are required to satisfy additional documentation requirements, determine coverage and/or prior auth applicability. For example, information about household composition, accessibility considerations, etc. This should be used when the data needs to come from the patient themselves, rather than a clinician's assessment of the patient
    conditionalConditionalThere is the potential for information requirements from a participant type not listed. However, a decision on whether there in fact are additional information requirements cannot be made without more information (more detailed code, service rendering information, etc.)

Source

{
  "resourceType" : "ValueSet",
  "id" : "AdditionalDocumentation",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet AdditionalDocumentation</b></p><a name=\"AdditionalDocumentation\"> </a><a name=\"hcAdditionalDocumentation\"> </a><a name=\"AdditionalDocumentation-en-US\"> </a><ul><li>Include these codes as defined in <a href=\"CodeSystem-temp.html\"><code>http://hl7.org/fhir/us/davinci-crd/CodeSystem/temp</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"CodeSystem-temp.html#temp-clinical\">clinical</a></td><td style=\"color: #cccccc\">Clinical Documentation</td><td>Details most likely to originate from a clinician are required to satisfy additional documentation requirements, determine coverage and/or prior auth applicability - e.g. via DTR by clinician. Indicates that the CRD client should expose the need to launch DTR to clinical users.</td></tr><tr><td><a href=\"CodeSystem-temp.html#temp-admin\">admin</a></td><td style=\"color: #cccccc\">Administrative Documentation</td><td>Administrative details not likely to require clinical expertise are needed to satisfy additional documentation requirements, determine coverage and/or prior auth applicability - e.g. via DTR by back-end staff. Indicates that while the CRD client might expose the ability to launch DTR as an option for clinical users, it should be clear that clinical input is not necessary and deferring the use of DTR to back-end staff is perfectly appropriate. Some CRD clients might be configured (based on provider preference) to not even show clinicians the option to launch.</td></tr><tr><td><a href=\"CodeSystem-temp.html#temp-patient\">patient</a></td><td style=\"color: #cccccc\">Administrative &amp; clinical doc</td><td>Details most likely to originate from the patient or their personal representative (e.g. parent, spouse, etc.) are required to satisfy additional documentation requirements, determine coverage and/or prior auth applicability. For example, information about household composition, accessibility considerations, etc. This should be used when the data needs to come from the patient themselves, rather than a clinician's assessment of the patient</td></tr><tr><td><a href=\"CodeSystem-temp.html#temp-conditional\">conditional</a></td><td style=\"color: #cccccc\">Conditional</td><td>There is the potential for information requirements from a participant type not listed. However, a decision on whether there in fact are additional information requirements cannot be made without more information (more detailed code, service rendering information, etc.)</td></tr></table></li></ul></div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger" : 1
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode" : "fm"
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode" : "trial-use",
      "_valueCode" : {
        "extension" : [
          {
            "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical" : "http://hl7.org/fhir/us/davinci-crd/ImplementationGuide/davinci-crd"
          }
        ]
      }
    }
  ],
  "url" : "http://hl7.org/fhir/us/davinci-crd/ValueSet/AdditionalDocumentation",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.4.642.40.18.48.1"
    }
  ],
  "version" : "2.1.0",
  "name" : "CRDAdditionalDoc",
  "title" : "CRD Coverage Information Additional Documentation Value Set",
  "status" : "active",
  "experimental" : false,
  "date" : "2024-12-11T01:38:49+00:00",
  "publisher" : "HL7 International / Financial Management",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/fm"
        }
      ]
    }
  ],
  "description" : "Codes defining whether additional documentation needs to be captured",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "urn:iso:std:iso:3166",
          "code" : "US"
        }
      ]
    }
  ],
  "compose" : {
    "include" : [
      {
        "system" : "http://hl7.org/fhir/us/davinci-crd/CodeSystem/temp",
        "concept" : [
          {
            "code" : "clinical"
          },
          {
            "code" : "admin"
          },
          {
            "code" : "patient"
          },
          {
            "code" : "conditional"
          }
        ]
      }
    ]
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.